chore: fill derivable placeholders, drop false ARCHITECTURE, surface the rest - #46
chore: fill derivable placeholders, drop false ARCHITECTURE, surface the rest#46hyperpolymath wants to merge 3 commits into
Conversation
…the rest
Estate top-up pass. Three separate things, none of which invents a value.
FILLED — every token with a single mechanical answer: OWNER, REPO, FORGE,
PROJECT, PACKAGE_NAME, PROJECT_NAME, AUTHOR, AUTHOR_EMAIL, CONDUCT_EMAIL,
AUTHOR_FIRST/LAST/INITIALS, CURRENT_YEAR, CURRENT_DATE, DATE, MAIN_BRANCH.
Identity comes from the git remote, dates from the clock, project name from the
README H1 where there is one.
Deliberately NOT filled, because more than one defensible answer exists and a
confident wrong value is worse than a visible gap: SECURITY_EMAIL (two competing
addresses are in use across the estate), RESPONSE_TIME, CONDUCT_TEAM (which
substitutes into "a {{CONDUCT_TEAM}} member", not English), WEBSITE,
PROJECT_DESCRIPTION, LANG_STACK.
DELETED — ARCHITECTURE.md, where it is byte-identical to the 346-copy estate
boilerplate (blob 607e3d8c). Those 33 lines describe a src/ tests/ docs/
scripts/ config/ tree that this repo does not have, so the file is not merely
uninformative, it is wrong. Genuinely written ARCHITECTURE files are matched by
hash and left alone. No file beats a confidently false one.
CODEOWNERS — rewritten to the solo form mandated by
hyperpolymath/standards CODEOWNERS-POLICY.adoc Rule 1, which forbids a catch-all
line where the only owner is the sole maintainer. The estate's own
templates/CODEOWNERS contradicts that policy; the policy is versioned, dated and
resolves standards#55, so it wins. Files naming a genuine co-owner are Rule 2
and are untouched. Note @hyperpolymath and @metadatastician are the same person,
so a file naming the other account is a copy artifact that silently routed
review requests to the wrong account.
SURFACED — REQUIRES_INITIALISATION.md, and a priority action in
0-AI-MANIFEST.a2ml. Tokens that need a decision no script can make are left
visibly unfilled rather than faked or quietly deleted. The marker says what each
one is, which files it belongs in, why it was not done already, and that it must
be deleted only once the work is genuinely finished.
|
Note Automatic reviews are paused because your trial's included automatic processing has been used for this period. Upgrade now, or comment "Gitar review" to run a review anytime. Code Review 🚫 Blocked 0 resolved / 2 findingsAutomated estate top-up populates derivable placeholders, removes boilerplate ARCHITECTURE files, and updates CODEOWNERS. Blocked due to PROJECT_NAME incorrectly deriving the 'What Is This?' template heading and a self-rejecting filter rule. 🚨 Bug: PROJECT_NAME filled from template heading, not real name📄 0-AI-MANIFEST.a2ml:10 📄 .guix-channel:9-10 📄 .guix-channel:17 📄 guix.scm:21 📄 guix.scm:66 📄 container/manifest.toml:14 📄 container/Containerfile:72 📄 docs/attribution/CITATIONS.adoc:8 📄 docs/attribution/CITATIONS.adoc:12 📄 docs/attribution/CITATIONS.adoc:19 📄 docs/attribution/CITATIONS.adoc:23 📄 docs/attribution/CITATIONS.adoc:27 📄 docs/attribution/CITATIONS.adoc:31 📄 docs/attribution/CITATION.cff:7 📄 container/ct-build.sh:49 📄 container/deploy.k9.ncl:25 📄 container/vordr.toml:3 📄 container/compose.toml:3 📄 container/.gatekeeper.yaml:3 📄 container/entrypoint.sh:3 📄 docs/architecture/THREAT-MODEL.adoc:5 📄 docs/architecture/THREAT-MODEL.adoc:11 📄 docs/architecture/THREAT-MODEL.adoc:37 📄 docs/developer/ABI-FFI-README.adoc:4 📄 docs/attribution/CITATION.cff:7 The top-up derived PROJECT_NAME from the README H1, but that heading is still the unfilled RSR template placeholder "What Is This?" (README.md:6). The repository's real name is
|
| Compact |
|
Important
Your trial ends in 5 days — upgrade now to keep code review, CI analysis, auto-apply, custom automations, and more.
Was this helpful? React with 👍 / 👎 | Gitar
![gitar-bot[bot]](https://avatars.githubusercontent.com/in/827041?s=60&v=4){kind=small}
| ;; (name 'What Is This?) | ||
| ;; (url "https://github.com/hyperpolymath/What Is This?") |
There was a problem hiding this comment.
🚨 Bug: PROJECT_NAME filled from template heading, not real name
The top-up derived PROJECT_NAME from the README H1, but that heading is still the unfilled RSR template placeholder "What Is This?" (README.md:6). The repository's real name is eclexiaiser (0-AI-MANIFEST.a2ml:10, manifest.toml homepage). As a result every {{PROJECT_NAME}} was replaced with the wrong string, and worse, the value contains a space and a ?, which breaks the syntactic contexts it was substituted into: .guix-channel and guix.scm now have (name 'What Is This?) / (name "What Is This?") and URLs like https://github.com/hyperpolymath/What Is This? (invalid Guix symbol and malformed URLs), .devcontainer/Containerfile has WORKDIR /workspaces/What Is This? and podman build -t What Is This?-dev (space splits the path/tag), and CITATIONS.adoc/CITATION.cff produce invalid BibTeX keys @software{What Is This?_2026, and spaced repo URLs. Replace the substituted value with eclexiaiser everywhere (and fix the README H1 to the real name so the derivation is correct on re-run).
Was this helpful? React with 👍 / 👎
|
|
||
| [methodology.state-validation] | ||
| reject-if-contains = ["{{PLACEHOLDER}}", "{{PROJECT}}", "rsr-template-repo"] | ||
| reject-if-contains = ["{{PLACEHOLDER}}", "ECLEXIAISER", "rsr-template-repo"] |
There was a problem hiding this comment.
⚠️ Bug: reject-if-contains now self-rejects on project's own name
In methodology.a2ml the state-validation guard changed from reject-if-contains = ["{{PLACEHOLDER}}", "{{PROJECT}}", "rsr-template-repo"] to ["{{PLACEHOLDER}}", "ECLEXIAISER", "rsr-template-repo"]. The list is meant to detect uninstantiated template markers; the original {{PROJECT}} was a token sentinel. Substituting the literal uppercase project name means any legitimate state file that mentions ECLEXIAISER (e.g. docs/developer/ABI-FFI-README.adoc now contains ECLEXIAISER ABI/FFI Documentation) will be wrongly rejected as corrupt/template. Restore a token sentinel such as {{PROJECT}} / {{PROJECT_NAME}} rather than the resolved name.
Was this helpful? React with 👍 / 👎
There was a problem hiding this comment.
Configure merge blocking · Maintainers can dismiss this review.
…t a value
The estate top-up sweep substituted {{PROJECT}} here along with every other
token. This line is a DETECTOR list: the comment above it says these rules
detect corrupt/template/stale state files, so the tokens named in it are the
ones whose PRESENCE means a state file is broken.
Substituting it did two things. It blinded the {{PROJECT}} leak detector, and it
made the detector reject any state file containing this repo's own uppercased
name — the opposite of what the rule is for.
Same failure class as a template recipe rewriting the incident record that
documents its own bug: substituting tokens inside a thing that is ABOUT tokens.
Nothing else in this PR changes.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The previous commit on this branch was written by a script that read the file through a shell command substitution. $(...) strips trailing newlines and printf '%s' does not put one back, so the file lost its final newline and the diff showed "\ No newline at end of file". Content is otherwise byte-identical to that commit. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Closing in favour of a reworked substituter — hyperpolymath/standards#590. This sweep filled Those are the scripts whose job is to perform template substitution. Filling the left-hand side of their own Four further shapes came out of the same cause:
The rule plain replacement cannot express: a placeholder is sometimes a value to fill and sometimes the subject being discussed. standards#590 encodes that distinction and is tested against this exact corruption (9/9, the first three cases reproducing it). Nothing here is lost — the placeholder filling will be redone with that tool. Closing rather than fixing forward because repairing 289 branches individually would repeat the mistake at the same scale. |
1 participant
Automated estate top-up. Nothing here invents a value.
Filled — every token with one mechanical answer (owner, repo, forge, author, dates, project name, main branch). Identity from the git remote, dates from the clock, name from the README H1.
Not filled, on purpose —
SECURITY_EMAIL(two competing addresses exist in the estate),RESPONSE_TIME,CONDUCT_TEAM(substitutes into "a {{CONDUCT_TEAM}} member", which is not English),WEBSITE,PROJECT_DESCRIPTION,LANG_STACK. More than one defensible answer exists, and a confident wrong value is worse than a visible gap.Deleted —
ARCHITECTURE.mdwhere it is byte-identical to the 346-copy estate boilerplate (blob607e3d8c). Those 33 lines describe asrc/ tests/ docs/ scripts/ config/tree this repo does not have. Matched by hash, so a genuinely written ARCHITECTURE can never be caught by it.CODEOWNERS — the solo form from
standards/CODEOWNERS-POLICY.adocRule 1, which forbids a catch-all where the only owner is the sole maintainer.templates/CODEOWNERScontradicts that policy; the policy is versioned, dated and resolvesstandards#55, so it wins. Genuine co-owners (Rule 2) are untouched.Surfaced —
REQUIRES_INITIALISATION.mdplus a priority action in0-AI-MANIFEST.a2ml, listing every remaining token, what it means, which files it belongs in, why it was not done already, and that it is to be deleted only when the work is genuinely complete.Built from a fresh clone of
origin/main, never a local checkout — several of those are dirty and hold unpushed commits.🤖 Generated with Claude Code